content: first flight, and the visibility that runs one way - #4
Open
fcatuhe wants to merge 3 commits into
Open
Conversation
…what it doesn't see) Closes launch-gate G9: the one page a stranger needs to flash a skyBlip Go and fly it. Covers the UF2 drag-and-drop first flash (and the one file to avoid), the settings a phone can change over BLE and the physical-presence gesture that authorises them, what each of the three alarm levels does (thresholds traced to core/traffic/alarm.h), and — as its own remembered section, not a footnote — what the device does not see: no OGNTP, no FANET, no PilotAware P3I, no 1090 or UAT978 on its own radio, and nothing at all from traffic that transmits nothing. English and French (content/first-flight, content/fr/premier-vol). Nav updated via page frontmatter; devices now links forward to it. No Web Bluetooth configuration page exists yet in skyblip/ or website/; the BLE section is written to be true today and says so.
…stays quiet in Each level has its own rhythm since core/annunciation landed: a blip, a pair, a train of six that repeats. And the limitation the committed circling fixture pins down belongs on the page a stranger reads, not only in the spec: two gliders on offset circles in one thermal can pass very close while the range never closes long enough to count.
No FLARM-generation display receives ADS-L: the licence those devices can buy is to transmit it. A reader of this page would otherwise assume mutual visibility from "transmits and receives", and the research behind that claim is project/research/does-flarm-receive-adsl.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Gate G9 of the launch gate asks that a stranger can flash a skyBlip Go and fly it, from one page. This adds that page in both languages, and corrects
see-and-avoidon the one fact a buyer would otherwise get wrong: no FLARM-generation display receives ADS-L, so visibility runs one way today.User flow
A pilot who has just been handed a device lands on
/first-flightfrom the nav or from the bottom ofdevices, and leaves knowing four things: how to put firmware on it (double-click, drag, drop), what a phone can change over Bluetooth and why the device asks for a button press before it accepts anything, what each of the three alarm levels sounds like and when it fires, and what the device cannot see. The French pilot gets the same page at/fr/premier-vol.Behavior changes
/first-flightand/fr/premier-vol, in the nav, linked fromdevicessee-and-avoidsaid we transmit and receive ADS-LImplementation notes
Every threshold on the page traces to a firmware constant, and each is named in the commit: the three alarm rings and the vertical window from
core/traffic/alarm.h, the vibration durations and re-announce interval from the alarm service, the 600 ms double press fromui/input/gesture.h, the 30 s prompt and 10 minute upload window fromcore/comms/config.h, the settings list fromschemas/config.v1.schema.json, and the bootloader behaviour fromscripts/mkuf2.pyand the UF2 spec.Design decisions
see-and-avoidrather than repeating it.see-and-avoid, not buried on the new page, because that is the page a prospective buyer reads before deciding whether this device makes them visible to the traffic they care about.Tests
bin/cigreen (style, gem audit, importmap audit, Brakeman).bin/static-buildgreen, emittingbuild/first-flight.htmlandbuild/fr/premier-vol.htmlwith nav, hreflang alternates and cross-page links resolving.